Meta-Access
Description
Meta-Access objects represent the data fields and access paths in the meta model. They are created automatically for data fields via the ObjectCrawler and manually for access paths with procedure or function calls. The master of a Meta-Access object is always a Meta-Object. In case the type of the return value of the Meta-Access object is a reference (object or list), the respective target objects are again meta objects.
Functionality
Input window
This window is used to maintain Meta-Access objects.
| Menu item | Description |
|---|---|
| Edit | - |
| : Validity | Set validity |
| Close | Closes the window |
| Search | Call up list window |
| Symbol | Description |
|---|---|
 | Create new Meta-Access object |
 | Save changes |
 | Delete Meta-Access object |
  | Print Meta-Access object |
 | Define validity of the Meta-Access object |
| Field | Description |
|---|---|
| : Identification | - |
| : : Access path | Data field or access printout with also procedure and function calls. It is the navigation path from an object to an elementary data field or to another object. |
| : : Master | The meta-object from which the access expression leads to the meta-access information described here. |
| : Type of the return value | - |
| : : Elementary data type | These are data fields of type String (character string), Integer (whole number), etc. These Meta-Access objects cannot have references. |
| : : Object | These are data fields of type pointer, REL_11, REL_1M or such access paths that return an object. |
| : : List | These are data fields of type Collections, REL_M1, REL_MN or access expressions that return collections of objects. |
| : : refers to | The meta-objects to which the access expression - if of type Object or Collection - refers. Even if the type of the return value of the access expression is an object (e.g.: itemPointer or FirstPredecessorByCondition()), it may be possible to refer to different (e.g. different derivatives of a class) meta objects. |
| Description | |
| : : Manually created | These are access expressions that were not read out via the object crawler, but created manually. |
| : : Special derivation | The access printout has a special, derived function at a customer or is only available there. Access expressions with this identifier are specially marked during import and export so that the user can decide whether or not to import or overwrite them. |
List window
This window is used to list the Meta-Access objects.
| Menu item | Description |
|---|---|
| Edit | - |
| : Reset | Reset the list: The list and search fields are cleared. |
| Close | Close window |
| Options | Call up the option window |
| Symbol | Description |
|---|---|
 | Perform multiple search: All fields that are marked blue are taken into account in this search. With the multiple search it is possible to search for several criteria at once. |
 | Reset the list: The list and search fields are cleared. |
| Create new Meta-Access object |
 | Edit Meta-Access object |
| Delete Meta-Access object |
| Print Meta-Access object |
| Set validity |
| Field | Description |
|---|---|
| Access path | Name of the access path |
Selection window
This window is used to select Meta-Access objects.
| Field | Description |
|---|---|
| Access path | Name of the access path |
Access Print Configurator
These windows allow you to configure access expressions. The corresponding representation of the transferred object ("data origin") is searched for in the meta model. From this meta object, it is now possible to navigate through the meta model to the target data. The access expression is composed on the basis of the meta-access elements passed through in this process.
Since the same access paths are often traversed when compiling the data format of a list, several access expressions can be configured together. Thus, for the configuration of several columns, navigation does not have to be started anew from the start object each time.
| Field | Description |
|---|---|
| : : Data origin | This is the start object from which the navigation to create the access sounds starts. It can be set by Drag&Drop, but is usually passed by the calling module. Thus, if an access expression is to be created for the report on the customer list, a customer object is also transferred to the list. |
| : Current path | - |
| : : List | Access expressions can be concatenated. Starting from an object A, one can navigate through the data fields b, c, and d one after the other via the objects B and C to D in order to access data fields of D. To know which is the current position - in this case D - the chain is shown in this list. ( "A |
| : : : Back | Via Back you can navigate one step back in the chain. |
| : : Start | Via start an access expression can be compiled again starting from the origin. |
| : Current position | - |
| : : Current position | Here the meta-object is displayed. Its access expressions are shown in the list. |
| : : List | The list shows the access expressions of the current position. By double-clicking on an elementary data type (string, integer, etc.) or a simple object (CX_VALUE, CX_DATE, etc.) a new access expression can be formed, which is then displayed in the list of selected access expressions. You can navigate further by double-clicking on a reference. The reference then becomes the next current position. |
| Arrow to the right | Via the list, a new access printout can be accepted by double-clicking. If you want to generate several access expressions directly from the current position, the corresponding lines in the list can be selected and copied by pressing the arrow key. |
| : Selected access expressions | |
| : : List | The created access expressions are displayed here. The name of the access expression can be edited by double-clicking. This is then taken over as column heading, for example, if the access expression configurator was called up from a corresponding module. |
Option window
All settings for the search can be made here. The window can only be closed with the "OK" button.
| Menu item | Description |
|---|---|
| Edit | - |
| : Set default settings | all changed settings are reset to default |
| Field | Description |
|---|---|
| List options | |
| : Search options | - |
| : : : Immediate take over in case of a hit | If a search only returns a ... is found during a search, it will be opened in the input window |
| : : : Clear list before new search | The list is cleared before each new search |
| : : General search | Normal search Search terms from ... use yourself |
| : : Advanced search | So-called wildcards can be used for the search like the * or AND OR... Search terms of the other roles of the ... will be considered |
| : Validity | Validity |
| : : With exchange object | |
| : : Without exchange object | |
| : : Only valid objects | |
| : : All objects | |
| : Number of objects | Determines the maximum number of objects in the list that can be displayed during a search |
| : : All objects | |
| : : Number of objects | |
| : : 100 objects | |
| Presets | |
| : Global presets | Global presets can be saved for the client and account. These are displayed here as well as the current default options that each module has. To create a global preset, a user preset must first be saved. With a right click on this user setting and selection of the context menu item "Edit user-defined setting" an editing window for this setting is opened, where the assignment of the employee / user to a client or a cost centre can be changed. (Button "Level") |
| : User Presets | Each user can save any number of presets. It is only important to note that if several settings are found, the first one found is used as the default setting. The name of the setting can be changed with a double-click. |
| button | Description |
|---|---|
| OK | The settings are saved and the window is closed. |
Related topics
Technical documentation
"Module" basic module
Module name
"module".mod
Classes
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | Security |
|---|---|---|---|
| Message | Parameters | Function | Receiver module |
|---|---|---|---|
"Module" editing module
Module name
"module".mod
Classes
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | Security |
|---|---|---|---|
| Message | Parameters | Function | Receiver module |
|---|---|---|---|
"Module" selection module
Module name
"module".mod
Classes
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | Security |
|---|---|---|---|
| Message | Parameters | Function | Receiver module |
|---|---|---|---|
;){kind=link}
;){kind=link}
;){kind=link}